∂12-OCT-74  1539		105,SGK
 Will you tell me where you are keeping E.  I plan to be working on E too, but
 all of what I do will be conditional and will not conflict with your work.
 I think it will work out better if we are keeping the things we both add in
 the same english, so my stuff will live in an up to date E.

∂10-OCT-74  1214		FOL,REF
 Suggestion for E:
 	How about a /Quiet switch when invoking the editor, which represses
 the "NEED TO REFORMAT" and "INVALID DIRECTORY" questions and answers.
 	Thus , "ET FOO/N/Q" would edit FOO without a directory page, and
 without asking if the page should be removed, and "ET FOO/Q" would create
 a directory page for FOO if it didn't have one, without asking.
 
 	Also, a ⊗XSQUASH command, which accomplishes the same effect
 as is presently gotten by the sequence ⊗E ET FOO/N <cr> N ⊗E ET FOO <cr> Y
 
 i.e. -- reformatting the file to take up a minimum of space.
 
 	Further suggestion.  A command which would "move the underbar
 up and down" (exit from the line, then α<space> as many spaces into the
 line as we were when we invoked the command) would help in the production
 of a lot of similiar lines.  If this notion were to be carried further, the
 ability for the user to string together a series of E commands, give it
 a name (using the unused control characters) would be a simple but
 effect macro facility.
 
 	I'd appreciate hearing from you as to the feasibility and
 desirability of these suggestions.  Thanks.
 			Bob Filman 

∂09-OCT-74  1511		1,BH
 If the command ET FOO←BAR finds file BAR.XYZ it should create FOO.XYZ

∂08-OCT-74  1331		ACT,REG
 αβAαβ-αβC crashes E with an illegal uuo at 105.  Perhaps you could fix it?

∂07-OCT-74  1247		S,LES
 I'm looking for some good words.

∂06-OCT-74  2136		FOO,DBA
 It would be nice if ETV <file> did ETV <file>/R if the file were write-protected.

∂03-OCT-74  0737		105,SGK
 The following bug has been introduced into E:

 When editing a line (it seems only a line which does not exist on DSK yet)
 typeing ↑. <Control Point> does not re enter the line editor properly.
 Normally, the line you were editing would be put back in the line editor,
 and your pointer would positioned as it was before.  I.E. ↑. has no
 noticable effect except that it leaves the line editor for a moment.
 At this time, ↑. seems to be reloading the line editor as would ↑XCAN <The extented
 command CAN>  More specifcally, ↑.'ing on a line which did not exist in
 the copy of the file on the DSK causes the line editor to be loaded with
 a copy of the TOP LINE(!) slightly modified.  
 	An easy way to see this happen is to create a file, type a few
 lines of text with different things in them so you can tell the difference
 between them.  Select a line which is not the top one, start line editing
 it and type ↑.  You will notice that the line editor will be restored with
 the top line of your file.
 	If this is not clear, let me know I will show it to you.

∂02-OCT-74  1945		1,DBX
 YOU WILL FIND MY COMMENTS ON TEACH IN TEACH[1,DBX].

∂30-SEP-74  1053		1,BH
 Idea for E: have a mode in which αF etc. searches ignore text between
 semicolon and crlf, so it only finds relevant instances of symbols.

∂28-SEP-74  0927		105,SGK AT TTY40   0927
 Could you point me at the code in E which moves the arrow in the left
 margin.  I am interested in seeing his DD program for doing this; my
 attempt at putting it all in one program failed because it took 4 revolutions
 of the DD.